Sams Teach Yourself MCSE Windows NT Server 4 in 14 Days
(Publisher: Macmillan Computer Publishing)
Author(s): David Schaer, et al
ISBN: 0672311283
Publication Date: 12/15/97

The network path is the location of the resource on the network. The UNC name that is most commonly used with Windows NT and bindery-based servers such as with NetWare 3.12 and earlier versions is \\servername\volume\directory However, when using NDS resources, separate each level of the tree with a period. The proper syntax is \\ndstree\volumename.orgunit.org

After you enter all the appropriate information, click OK and the gateway is added. Notice that you can add more than one gateway by clicking the Gateway button again.

After the gateway is established, it appears in a Configure Gateway dialog box similar to Figure 12.8. You handle permissions by clicking the Permissions button. Configuring permissions on the gateway is identical to configuring permissions on a directory that is local to the server. The drive shows up as a network drive in the My Computer and Explorer interfaces. On the client machine, it appears as a share on the Windows NT computer that is configured with the GSNW.

The only available type of security for the gateway is share security. You do not have the capabilities of NTFS security.

Figure 12.8.  Viewing the NetWare gateways.

You can share NetWare print queues through the gateway by clicking the Add Printer icon in the Printers folder. Using the Add a Printer Wizard, you should select that you will connect to a network print server. After you have done so, you can browse for the printer or enter the UNC path (see Figure 12.9).

Figure 12.9.  Selecting the NetWare print queue to connect to using the Add a Printer Wizard.

During normal connections to network print servers, Windows NT automatically downloads the driver from the remote server. However, because NetWare servers do not use Windows-based drivers, Windows NT prompts you to select which printer you want to install. This lets you load the driver using the Windows NT CD-ROM or using driver disks from the manufacturer of the printer.

After the printer is installed properly, you can use the printer locally on the Windows NT server. Click the printer icon with your secondary mouse button and select Properties. In the property sheet for the printer, select the Sharing tab. Now simply share it to t he network. When you share it, clients can access it by connecting to the Windows NT server. Any print jobs are rerouted to the NetWare print queue via the GSNW.

12.3. NWLink, the IPX/SPX Compatible

Connectivity to NetWare requires the use of NWLink (short for NetWare Link), Microsoft’s protocol that is compatible with Novell’s IPX/SPX (Internetwork Packet Exchange/Sequenced Packet Exchange) protocol.

NWLink is required in situations in which you must make connections to NetWare servers or where NetWare clients must access Microsoft resources. NWLink supports Novell NetBIOS, Windows Sockets, Remote Procedure Calls, and named pipes.

12.3.1. Integrating Application Servers

Because NWLink supports Windows Sockets (WinSock ), you can use NWLink with applications that are specifically written for NetWare’s IPX/SPX Sockets interface, allowing the Microsoft clients to access NetWare servers for client/server applications. Additionally, NWLink also allows NetWare clients to access client/server applications on Windows NT servers. Examples of client/server applications include Microsoft SQL Server and Microsoft SNA Server host connectivity.

Installing NWLink alone does not give you full connectivity to NetWare due to the fact that NWLink does not include a NetWare-compatible redirector. To use the file and print services of NetWare, you must install the Gateway Service for NetWare.

The Client Service for NetWare and Gateway Service for NetWare included with Windows NT gives you connectivity to Novell NetWare servers. However, they do not give NetWare clients access to Windows NT servers. Available as an add-on, the File and Print Services for NetWare (FPNW) utility gives NetWare clients access to shares and printers on a Windows NT server. Directory Service Manager for NetWare (DSMN) allows integration of user and group accounts between NetWare and Windows NT servers. This utility lets you manage all user accounts on the network through the User Manager for Domains. Because FPNW and DSMN are add-on utilities, knowing extended information about them on the exam is not necessary.

12.3.2. Installing NWLink

You can add NWLink as a protocol through the Network applet of the Control Panel. Figure 12.10 shows the Protocols tab of the Network applet. Clicking the Add button produces a list of available protocols to be installed (see Figure 12.11).

Figure 12.10.  The Protocols tab of the Network properties dialog box is where you can add, remove, and update network protocols.

Figure 12.11.  Adding NWLink from the list of network protocols.

After you add NWLink, you can configure it by clicking the Properties button or by double-clicking NWLink in the list of protocols. When you open the NWLink Properties dialog box (see Figure 12.12), you notice two tabs, General and Routing.

Figure 12.12.  Viewing the NWLink properties dialog box.

Under the General tab, you can configure different items including the network number, which adapter will use NWLink, and the frame type. The network number is an eight-digit hexadecimal identification number, which assigns a logical network for NetWare servers. It allows identification of NetWare servers running on a multinet host.